test(maestro): size the resume wait for the observed propagation tail - #693
Open
Sarath1018 wants to merge 1 commit into
Open
test(maestro): size the resume wait for the observed propagation tail#693Sarath1018 wants to merge 1 commit into
Sarath1018 wants to merge 1 commit into
Conversation
The pause/resume test asserts resume was accepted, then waits for the instance to report Running again. That Paused->Running propagation typically lands in ~5s but has been observed to exceed the previous 20s window under tenant load, failing the test on a transition that was already in flight. Widen the wait to 60s (poll exits as soon as Running is reached, so healthy runs are unaffected). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
✅ No issues found. Checked for bugs and CLAUDE.md compliance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pause/resume test asserts the resume call was accepted, then waits for the instance to report Running again. That Paused→Running propagation typically completes in ~5s but has been observed to exceed the previous 20s wait under tenant load, flaking the test on a transition that was already in flight. The wait is now sized for the observed tail (60s); the poll exits as soon as Running is reached, so healthy runs are unaffected.
Verified green in both init modes.
🤖 Generated with Claude Code